Please take a look at these updates

@odobosh-lohika-tix Sorry for the delay. It appears all non-integer numbers are being treated as decimals... what about floats?

@techniq thank you for your notice.
Extended number with double type, added decimal as new type, updated README.
There is a small issue: Double type in js could be represented with 17 precision while 15 in oData specification.

@odobosh-lohika-tix Thanks for all the work on this. I see you linked to the OData 2.0 spec. Is this still relevant with OData 4.0? For some reason, I was thinking this was removed (and unneeded). I've used Decimal's in my projects in the past and did not require this change.

@techniq You are right - it was removed in v3 of odata.
But some OData implementations still have some gaps and troubles parsing numeric values. In particular there is a problem in .NET implementation which is by far the most popular(OData/odata.net#461). This little fix will allow the client just explicitly set the type of the value if they want to do so to close the gap, without resorting to raw type.

So no need in double type but we can leave decimal type (as separate one).

@odobosh-lohika-tix That works for me. Thanks for the PR!

@odobosh-lohika-tix Released as 6.7.0. Thanks again!